Skip to content

[No QA] Unify avatar sizes - #95275

Open
jmusial wants to merge 16 commits into
Expensify:mainfrom
software-mansion-labs:chore/unify-avatar-sizes-v2
Open

[No QA] Unify avatar sizes#95275
jmusial wants to merge 16 commits into
Expensify:mainfrom
software-mansion-labs:chore/unify-avatar-sizes-v2

Conversation

@jmusial

@jmusial jmusial commented Jul 3, 2026

Copy link
Copy Markdown
Contributor

Explanation of Change

Replaces the legacy ad-hoc avatar sizes (SMALL_NORMAL, HEADER, LARGE_BORDERED, …) with a linear xxxx-small (12px) → xxxx-large (100px) scale backed by centralized tokens and exhaustive style maps. Unifies how avatar borders are handled.

Visual changes

None - all sizes are pixel-identical. The two spots where new defaults would have differed (subscript border on 100px avatars, workspace avatar radius in RoomHeaderAvatars) keep their old values explicitly. (AttendeesCell's stacked-row container now includes the avatar border in its height for consistency with other stacks — layout-neutral, row height is padding-driven.)

Dead code

Removed HeaderView's 32px SMALL_NORMAL subscript branch — unreachable, since ReportHeader sends all expense-request reports to MoneyRequestHeader first.

Fixed Issues

$ #95598

PROPOSAL:
Coming from this thread

Tests

Refactor mostly without impact for the user, some basic tests:

  1. Open app
  2. Navigate through pages, verify that avatar sizes are the same as on prod/staging.

Offline tests

Same as tests

QA Steps

N/A

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
    • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I followed proper code patterns (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I followed the guidelines as stated in the Review Guidelines
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
  • If new assets were added or existing ones were modified, I verified that:
    • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
    • The assets load correctly across all supported platforms.
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

MacOS: Chrome / Safari
Screen.Recording.2026-07-07.at.16.34.32.mov

@jmusial

jmusial commented Jul 3, 2026

Copy link
Copy Markdown
Contributor Author

@codex review

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 0787653f3d

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread src/styles/utils/index.ts
@codecov

codecov Bot commented Jul 3, 2026

Copy link
Copy Markdown

Codecov Report

✅ Changes either increased or maintained existing code coverage, great job!

Files with missing lines Coverage Δ
src/CONST/index.ts 94.81% <ø> (ø)
src/components/AccountManagerBookCallButton.tsx 100.00% <ø> (ø)
src/components/AvatarButtonWithIcon.tsx 100.00% <ø> (ø)
src/components/AvatarSelector.tsx 100.00% <100.00%> (ø)
src/components/HeaderWithBackButton/index.tsx 89.21% <ø> (ø)
src/components/ImportedFromAccountingSoftware.tsx 0.00% <ø> (ø)
src/components/OnboardingHelpDropdownButton.tsx 95.65% <100.00%> (+0.41%) ⬆️
src/components/ReceiptEmptyState.tsx 97.67% <100.00%> (+0.05%) ⬆️
src/components/ReportActionItem/TaskView.tsx 85.71% <ø> (ø)
...m/TransactionPreview/TransactionPreviewContent.tsx 79.83% <ø> (ø)
... and 50 more
... and 14 files with indirect coverage changes

@jmusial

jmusial commented Jul 3, 2026

Copy link
Copy Markdown
Contributor Author

@codex review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Hooray!

Reviewed commit: 6b060a8646

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

@jmusial jmusial changed the title Unify avatar sizes [No QA] Unify avatar sizes Jul 7, 2026
@jmusial jmusial mentioned this pull request Jul 9, 2026
43 tasks
@jmusial

jmusial commented Jul 24, 2026

Copy link
Copy Markdown
Contributor Author

@codex review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Keep it up!

Reviewed commit: 9edb8b62f6

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

@jmusial
jmusial marked this pull request as ready for review July 24, 2026 11:34
@jmusial
jmusial requested review from a team as code owners July 24, 2026 11:34
@melvin-bot
melvin-bot Bot requested review from ChavdaSachin and removed request for a team July 24, 2026 11:35
@melvin-bot

melvin-bot Bot commented Jul 24, 2026

Copy link
Copy Markdown

@ChavdaSachin Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@melvin-bot
melvin-bot Bot requested review from joekaufmanexpensify and removed request for a team July 24, 2026 11:35
@jmusial

jmusial commented Jul 24, 2026

Copy link
Copy Markdown
Contributor Author

cc. @roryabraham the unification of Avatar sizes. also cc @Expensify/design as this came of our discussion.
There should not be any user noticeable changes.

Comment thread src/components/ReportActionAvatars/ReportActionAvatar.tsx Outdated

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 79b05124e1

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

<ReportActionAvatars
reportID={report?.reportID}
size={shouldShowSubscript ? defaultSubscriptSize : undefined}
singleAvatarContainerStyle={[styles.actionAvatar, styles.mr3]}

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Restore the fallback 32px expense-thread avatar size

When an expense-request thread is opened before its parent report action collection is available, ReportHeader computes isReportTransactionThread(report) as false and mounts HeaderView; ReportHeader does not subscribe to that parent action, while HeaderView does via useParentReportAction, so this component can stay mounted after shouldReportShowSubscript() becomes true. Without the removed isExpenseRequest(report) size override, those direct/deeplinked expense-thread headers render the subscript avatar at the default 40px size instead of the previous 32px size, causing a visible header layout regression. Please keep the 32px mapping here or make the header variant selection reactive to the parent action.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removing 32px size is intentional per comment here

@joekaufmanexpensify joekaufmanexpensify left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good for product.

roryabraham
roryabraham previously approved these changes Jul 25, 2026

@roryabraham roryabraham left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall huge fan of this change. It's definitely bit tricky to sort through, so thank you for doing it! Much more orderly now.

Comment thread src/styles/utils/index.ts Outdated
Comment thread src/styles/utils/index.ts Outdated
Comment thread src/styles/variables.ts Outdated
@roryabraham

Copy link
Copy Markdown
Contributor

@ChavdaSachin awaiting C+ review on this PR

Comment thread src/styles/index.ts Outdated
@jmusial
jmusial dismissed stale reviews from roryabraham and joekaufmanexpensify via fe7e20c July 27, 2026 09:53
roryabraham
roryabraham previously approved these changes Jul 28, 2026
@roryabraham

Copy link
Copy Markdown
Contributor

Back to you @ChavdaSachin

@ChavdaSachin ChavdaSachin left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! ✅

@melvin-bot
melvin-bot Bot requested a review from roryabraham July 29, 2026 04:04
@ChavdaSachin

Copy link
Copy Markdown
Contributor

Reviewer Checklist

  • I have verified the author checklist is complete (all boxes are checked off).
  • I verified the correct issue is linked in the ### Fixed Issues section above
  • I verified testing steps are clear and they cover the changes made in this PR
    • I verified the steps for local testing are in the Tests section
    • I verified the steps for Staging and/or Production testing are in the QA steps section
    • I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I checked that screenshots or videos are included for tests on all platforms
  • I included screenshots or videos for tests on all platforms
  • I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
  • I verified tests pass on all platforms & I tested again on:
    • Android: HybridApp
    • Android: mWeb Chrome
    • iOS: HybridApp
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
  • I verified proper code patterns were followed (see Reviewing the code)
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I verified that this PR follows the guidelines as stated in the Review Guidelines
  • I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately
    • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
    • The only data being stored in the state is data necessary for rendering and nothing else
    • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
  • I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp
Android: mWeb Chrome
iOS: HybridApp
iOS: mWeb Safari
MacOS: Chrome / Safari

@ChavdaSachin

Copy link
Copy Markdown
Contributor

Something is broken on the latest main branch, due to which the avatar for the expense reports isn't loading....
Waiting for that to be resolved...

@jmusial

jmusial commented Jul 29, 2026

Copy link
Copy Markdown
Contributor Author

Something is broken on the latest main branch, due to which the avatar for the expense reports isn't loading.... Waiting for that to be resolved...

merged latest, I think it's ok now (seems normal for me)

@roryabraham

roryabraham commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

Awaiting @ChavdaSachin to complete the checklist

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants